I have a question regarding a semantic HTML construct, and I'd like to know what the current consensus is (if there is one). So here goes:

Should navigation links be placed in an unordered list in a <nav>?

The spec doesn't recommend anything, but examples from MDN (developer.mozilla.org/en-US/do…) and WHATWG (html.spec.whatwg.org/multipage…) consistently use lists unless the contents are written in prose. Is this still the preference more broadly?

I have some other questions in this area. Safari removes list semantics if you remove the bullets (with exceptions, such as if the list is a child of "nav"), due to alleged "list-itis". At what point do lists become inappropriate? If I have a list of blog posts, and I format them as cards, with a heading, publish date, summary, and an image, is that too much content for each <li>?

Also, MDN and WHATWG point out not all links should be contained in navs (such as footer links), and "nav" should instead signal major blocks of navigation links. Would my prior example of a list of blog posts count as a major block? Should I enclose my list of blog posts in a nav? Does that extend to all section, category, and tag pages listing pages in that section/category/tag?

Feel free to respond if you have opinions, but keep it civil, and boosts are appreciated.

#HTML #semanticHTML #WebDev #website #accessibility #a11y

: The Navigation Section element - HTML: HyperText Markup Language | MDN

The

^{MDN Web Docs}

Are you involved in digital accessibility outside the United States? I welcome updates to my global law and policy page - and I'd especially like to hear how laws and policies are implemented outside the United States.

I'm getting ready for Part 2 of my digital #accessibility legal update coming up on December 7. Free and online. Global page is here: lflegal.com/global-law-and-pol… You can register for the webinar here: go.3playmedia.com/wbnr-11-30-2… #a11y

The #UPowerWAD project is an #EU project to empower disabled users to exercise their rights regarding the Web #accessibility directive and report issues regarding public sector websites: funka.com/en/projekt/upower-wa…

#a11y

Equipped with a fresh pot of tea and reading Keyboard accessibility myths and #WCAG by @graeme on the @TetraLogical blog:
tetralogical.com/blog/2023/11/…

#accessibility #a11y

Keyboard accessibility myths and WCAG - TetraLogical

Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.

^TetraLogical

So I wrote a blog post for the first time in 5 years, warning about hcaptcha's accessibility account. Long story short, they banned me from the accessibility account because I'm not blind. I am blind, but well, they seem to think not. Please boost, share, etc since this seriously affects me, and it's not ok at all. You can read the full blog post here: 4mt.me/hcaptchastory

#blind #hcaptcha #a11y #accessibility #boost

Happy Firefox 120 release for those who celebrate 🎉

This comes with a couple important Debugger fixes and a bunch of accessibility improvements in the toolbox.

Grab your drink of choice and read through the full update fxdx.dev/firefox-devtools-news…

#Firefox #a11y #webdev

Did you know @kde had an #accessibility inspector? Currently it's hidden in the build folder of libqaccessibilityclient but not for long. We started the process of making it a standalone application and a first release is planned in 2-3 weeks!

apps.kde.org/accessibilityinsp…

#a11y #linuxDeskop

Congratulations to Gene, recipient of this year's RNZFB Chair's Award. It is wonderful to see your hard work & advocacy over many years acknowledged with this prestigious award. Gene has long advocated for NVDA & been a great friend to us in New Zealand. We're excited to see him honoured.

Read more at: blindlowvision.org.nz/news/cha…

#Blindness #Blind #Advocacy #RNZFB #BlindLowVision #A11y #Accessibility #NVDA #NVDAsr #ScreenReader

Related: 4 examples of web-accessible date pickers...

WAI: w3.org/WAI/ARIA/apg/patterns/d…

Deque: dequeuniversity.com/library/ar…

U.S. Web Design System
designsystem.digital.gov/compo…

Tommy Feldt: fymmot.github.io/inclusive-dat…

#date #calendar #UIDesign #webdesign #webdev #a11y

Date Picker Dialog Example

Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).

^{W3C Web Accessibility Initiative (WAI) (Web Accessibility Initiative (WAI))}

A super cool course: Accessible Technology Design, by AccessibleEU (free, online, self-paced, in English).

This introductory course consists of 6 modules:

1. Accessibility and Inclusive Design.
2. ICT Accessibility Laws and Standards.
3. Web Content Accessibility Guidelines (WCAG).
4. Digital Accessibility Myths.
5. Avoiding Non-Inclusive Design Patterns.
6. Creating Inclusive Designs.

accessible-eu-centre.ec.europa…

#a11y

Sign-up to AccessibleEU’s new Accessible Technology Design course!

The course is available on the AccessibleEU online campus. It ends on 15 December.

^AccessibleEU

"Access to a free, fast & efficient screen reader has changed my life. Because of its qualities, my computer never crashes; updates are frequent & the software works well. It follows best the evolution of Windows and all software. Updating is fast & easy, it is available in all languages. The provision of add-ons makes it really efficient” – Silvie, France

You can help continue to provide NVDA free to all! nvaccess.org/support-us/#donat…
#NVDA #NVDAsr #ScreenReader #Access #Accessibility #A11y

Today's Web Design Update: groups.google.com/a/d.umn.edu/… Subscribe info: d.umn.edu/itss/training/online… #Accessibility #A11y #WebDesign

Featuring @siblingpastry, @aardrian, @rachael, @ben, @reidmore, @ericwbailey, @cferdinandi, @karlgroves, @matuzo, @michelle, @adactio, @baldur, @mgifford, @andy_blum, @screenspan, @gerrymcgovern et al.

About CSS prefers-reduced-transparency:

developer.chrome.com/blog/css-…

#UIDesign #CSS #usability #a11y

CSS prefers-reduced-transparency - Chrome for Developers

Optimize and adjust for users who prefer an opaque UI.

^{Chrome for Developers}

See the nominees for Innovation in Accessibility for this year's Game Awards

thegameawards.com/nominees/inn…

#Gaming #VideoGames #TheGameAwards #TGA #a11y

The Game Awards

Check out the nominees for Innovation in Accessibility at TheGameAwards.com. Who will you vote for? #TheGameAwards @TheGameAwards

^{The Game Awards}

📝 New post! “Lost in Translation: Tips for Multilingual Web Accessibility”

Does your site's accessibility hold up across languages?

I wrote about the practical tips I wish I'd had for making sure that accessibility efforts and internationalization/localization efforts alike don't leave out disabled speakers of other languages than our own.

benmyers.dev/blog/multilingual…
#accessibility #internationalization #a11y #i18n

Lost in Translation: Tips for Multilingual Web Accessibility

Practical tips I wish I'd had for navigating the intersection between web accessibility and internationalization/localization.

^{Ben Myers}

It’s been 5 months since Australian Story aired an episode on NV Access founders, Mick Curran & Jamie Teh. The first Australian Story episode to be audio described. It was an incredible opportunity to share with a wider audience the importance of NVDA & our overarching message, that everyone deserves equal access to technology.

You can still watch the Australian Story episode, with Audio Description, on YouTube: youtube.com/watch?v=3i7gkN-1sA…
#ScreenReader #NVDA #NVDAsr #Accessibility #A11y #Access

The problem with disabled buttons and what to do instead:
adamsilver.io/blog/the-problem…

Disabled buttons suck:
axesslab.com/disabled-buttons-…

#UIDesign #forms #usability #a11y #accessibility

Disabled buttons suck

Showing buttons as disabled until a form is complete might seem like a good idea. It is not. They usually create a lousy user experience and exclude many people with disabilities. Here's why disabled buttons suck and what to do instead.

^{Hampus Sethfors (Axess Lab)}