Cassie said: Nick S., I appreciate your feedback. We learned a lot from you previous reviews of character sheets and are working toward making improvements with this layout that we can carry forward into other character sheets. I have been testing a personal project with ChromeVox and realized too late in this project that those 'y' buttons are a challenge when navigating by audio. I believe I have found a solution for adding a helpful label for screen readers which I intend to add in a future update. On the Pathfinder Second Edition sheet the 'y' buttons are used to show and hide input fields for visual users. Similarly you may encounter '4' buttons which show and hide notes or description text from visual users. From my brief testing of the sheet with ChromeVox, I was able to tab to the visually hidden areas without needing to activate the 'y' or '4' buttons. As a visual user when navigating this way I couldn't see these inputs or text areas but the audio informed me that I was accessing them via the keyboard. I will add that issue with the "custom" input as an issue to address. I believe I know how we can stop that from being automatically set when navigating the character sheet. As a novice screen reader, I do not yet know how to navigate by headers, buttons, and other elements so I can certainly replicate this experience in testing. There are a number of places we want to update the HTML elements we used to allow for better audio navigation particularly using headers. Thanks for taking the time to reply. Let me know anything else you have feedback for. - Cassie Cassie, My initial response to your statement is this. Chromevox is not a very good representation of accessibility. I would recommend downloading the free NVDA screen reader from nvaccess.org If you use this screen reader for testing with Mozilla Firefox it will give you much better results for making the sheet accessible for the overwhelming majority of screen reader users of Roll20 on Windows, as NVDA is comparable to the main screen reader used by the majority of those users. That main screen reader costs money, however, so it wouldn't be good to use for testing purposes. I figured that the "y" buttons and "4" buttons did exactly what you described, although I would appreciate it if these buttons also hid the fields from screen readers as the Pathfinder first edition and Starfinder sheets do. It's excellent that the sheet can be navigated by heading and this has been implemented wonderfully. I would still like to be able to hide the clutter from my screen reader though for navigating within the different sections. The way that works in the first edition Pathfinder sheet is ideal. If this isn't possible with the way this sheet is written it does work well the way it is currently. As for navigating with screen readers by headings, buttons and the like, I can help you with this if you use the NVDA screen reader mentioned above. Chromevox has changed how to do this several times and I'm not sure how it works anymore. Web pages use a system called single key navigation, where you press one key to jump to a specific element and to navigate to the previous one you use the same key while holding down shift. I'll list a couple of the elements below and they're associated keys. headings h buttons b check-boxes x combo boxes c edit text fields e form controls in general f (This includes all the controls I've just listed along with a few others, except for headings) If you wish to enter text into a field or change the values in a combo box, press enter on that control, and a beeping noise will indicate that you're in focus mode. This allows you to edit that control. When you're done with that press escape. Sometimes the screen reader will enter you into focus mode automatically, but you can get out by pressing escape at any time.