You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: I'm not shure if this is the right place to put this note.
Although #3942 lays out the goal that "[...] The Getting Started section should contain everything you need to build a new application from scratch and deploy it to production (the "happy path"). It should be very hands-on, focusing on what you need to do rather than why."
I'd like to request that you take a11y into account when writing the "skeleton application". I followed most of the tutorial for hilla and ran a A11y check via Vaadin Copilot afterwards but got some red alerts because of missing landmark elements. The tutorial uses <header>. <SideNav> sets the correct role attribute. But there were no other landmarks, for example <main> used in the tutorial. Additionally the tutorial put the page title into the navbar slot - which looks good but from a visual perspective - but caused one of the red alerts from a11y check. If you have an idea how to solve that, the tutorial should already contain that solution.
I don't want to request that you describe those elements in lengthy detail in the tutorial. Maybe you don't describe them at all but the examples should contain the necessary boilerplate to produce an accessible app "the vaadin way".
Based on the concept of a Walking Skeleton.
The text was updated successfully, but these errors were encountered: