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
I'm finding the redesigned site's navigation to be a little frustrating, specifically with links in the header. For example: if you go to the index page for the Understanding docs, there's no link in the site header to get back to the homepage. I can get to an "about" page for Understanding docs, or the WAI homepage, but not the homepage for the version of WCAG I'm looking at. To add to the frustration, removing the Understanding part of the URL to leave https://www.w3.org/WAI/WCAG22/ results in a "Sorry, Insufficient Access Privileges" page rather than, as I'd hoped, the WCAG 2.2 homepage. Confusingly, further removing WCAG22 from the URL does result in the WAI homepage being loaded.
I realize that re-designing the site header is probably a pain, but fixing the URL structure so that https://www.w3.org/WAI/WCAG22/ does load the WCAG 2.2 homepage would be appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm finding the redesigned site's navigation to be a little frustrating, specifically with links in the header. For example: if you go to the index page for the Understanding docs, there's no link in the site header to get back to the homepage. I can get to an "about" page for Understanding docs, or the WAI homepage, but not the homepage for the version of WCAG I'm looking at. To add to the frustration, removing the Understanding part of the URL to leave https://www.w3.org/WAI/WCAG22/ results in a "Sorry, Insufficient Access Privileges" page rather than, as I'd hoped, the WCAG 2.2 homepage. Confusingly, further removing WCAG22 from the URL does result in the WAI homepage being loaded.
I realize that re-designing the site header is probably a pain, but fixing the URL structure so that https://www.w3.org/WAI/WCAG22/ does load the WCAG 2.2 homepage would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions