Hi. Here's a follow up from the issue  about naming convention for accessibility related files.
Apparently Chromium project sticks with an implicit rule to give a file name matching its class name (with a number of exceptions for example unit test files). The rule is also encouraged by Google C++ Style guide :
"In general, make your filenames very specific. For
http_server_logs.h rather than
logs.h. A very common case is to have a pair
of files called, e.g.,
foo_bar.cc, defining a class called
This is a reasonable recommendation since it links class names and file names. However it has an unpleasant side effect in accessibility. Accessibility doesn't have its own namespace and thus most of the a11y files are prefixed by either by accessibility_ or by ax_, which makes literally all file names starting from those prefixes in certain folders. I think it obscures folder structure and makes it harder to spot a needed file when you look at a folder.
Long story short as part of a11y inspect refactoring, all inspect related files are moved under ui/accessibility/platform/inspect folder; all classes get AX prefix, but no ax_ prefix for the file names there . It seems that this is not very aligned with existing practices though. I wonder though if this case makes a good exemption from the rule.
So I'm eager to hear your opinion on how file names should be schemed in accessibility, whether it'd be good (or bad) to omit ax_/accessibility_ prefixes in folders containing accessibility files only.