(AKA The English Language Naming Convention)
Most of the work of creating good names is simply figuring out what a non-programmer would call something. If you are earning your living programming, you're probably near non-programmers. Ask one of them about your code.
The names of subprogram units are the most important names in a modular architecture because most of your code will be calls to other subprograms. You simply cannot write readable, understandable code unless the name of each subprogram describes its function. If the subprogram is a function, its function is to return a value so the names of function should indicate the identity of the expected result.
Every other good name you choose is a step in the right direction, but good subprogram names are critical. This is particularly true if you practice modularity because most routines will primarily consist of calls to other routines.
Forms and controls are two that quickly come to mind. Of course, there are lots of different kinds of controls, but that doesn't necessarily make the job any harder.
You got your tables, you got your fields, and you got your queries. Having this information public is essential to the operation of any database, and this exposure makes proper, stable names for these entities extremely important.
HTML files are used across a broad variety of environments and should be as usuable as possible in each of those environments.