I think it's a good idea, but we have to be very careful not to break existing applications. WCAG compliance is not as simple as sprinkling some attributes over your dom. For our application we had to significantly alter the markup in several places. I fear that if we make changes to the markup Wicket produces, it will break existing applications that already deal with WCAG. The good news is that we can use our application to test many of these changes. Our automated tests perform axe-core scans after almost any interaction and will catch incorrectly placed aria attributes.
The pull request for the lang on the head seems safe. It does however depend on users setting the locale correctly. I guess that's ok, because you'll get incorrect messages (such as feedback) all over the place if you do not do that. Emond Op zo 8 nov 2026 om 23:28 schreef Martijn Dashorst <[email protected]>: > > All, > > I intend to make wicket more accessibility compliant (WCAG 2.2 AA) in > the coming releases, which should benefit all downstream applications > to comply with laws and regulations regarding accessibility. > > The first step is doing an audit on the wicket code for accessibility. > This was performed in this PR and it has the findings in the comment: > https://github.com/apache/wicket/issues/1838#issuecomment-6705995932 > > From this a couple of fixes are under way. > > The first one is adding lang and dir (direction) attributes to the > <html> tag. This will affect all output, so golden files (like we have > in wicket tests) will break unless you already were compliant. The > idea is to take the language from the session, and use the direction > detection from the session as well. More information here: > https://github.com/apache/wicket/pull/1870 > > The second is adding a chapter on accessibility in the user reference. > This is PR https://github.com/apache/wicket/pull/1847 > > Please review and provide feedback. > > Thanks! > > Martijn
