Actually, it's okay for UML diagrams to not include lots of things that are in the class. UML does not have to provide a complete description of the code -- just the things that are useful/relevant to the discussion you want to have.
Thus, just because a field or method does not appear in a UML diagram, that doesn't mean that it isn't part of a class.
getters & setters are just one example of things that often aren't very useful to include in UML, because they take up space without adding a lot of value to the discussions you might have with other developers.
