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
because people could be bookmarking the current functional location, it seems like we should change the redirect to point to the functional location. Then, we land Pull Request #2597 and add another redirect to the renamed file.
because people could be bookmarking the current functional location, it seems like we should change the redirect to point to the functional location. Then, we land Pull Request #2597 and add another redirect to the renamed file.
Should we leave the redirect as is and rename content/patterns/landmarks/examples/HTML5.html to content/patterns/landmarks/examples/html5.html? Perhaps add this change to w3c/aria-practices#2597?
I looked into the datagrids and layout grids a little bit more and found that the WAI website seems to automatically remove capitalized letters from URLs. This is why the links on the site work but bookmarked pages don't.
I think the pages already have a bit of a strange naming convention, given that no other pages have capitalized letters, so a good solution would probably be to rename those two files in the aria-practices repo and introduce new redirects from the old urls to the new ones.
@mcking65@a11ydoer we can safely merge w3c/aria-practices#2597 and following that I will create a new publication branch, inform the WAI team, and document the changes we need to make to the redirects.
We have 4 legacy URLs that still lead to 404 errors.
Data Grids Example Page
because people could be bookmarking the current functional location, it seems like we should change the redirect to point to the functional location. Then, we land Pull Request #2597 and add another redirect to the renamed file.
Layout Grids example page
because people could be bookmarking the current functional location, it seems like we should change the redirect to point to the functional location. Then, we land Pull Request #2597 and add another redirect to the renamed file.
Landmark Examples: HTML Sectioning Elements page
Should we leave the redirect as is and rename
content/patterns/landmarks/examples/HTML5.html
tocontent/patterns/landmarks/examples/html5.html
? Perhaps add this change to w3c/aria-practices#2597?Landmark Examples: General Principles page
Is the best solution to change the redirect to point to functional location 1?
@alflennik wrote:
Originally posted by @alflennik in #186 (comment)
The text was updated successfully, but these errors were encountered: