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}

With the help of ChatGPT I have added alt text to images in my slide deck "No Industry for Old Men" from #a11yTO 2023

#a11y #webStandards #HTML #ARIA #Depression #aging #ai

docs.google.com/presentation/d…

No industry for old men

^{Google Docs}

Not picking on anyone, but I just saw someone asking devs not to use "2FA" in user messages, and instead use "two factor authentication."

2FA is 3 syllables. Two factor authentication is 8.

From my #a11y use case, 2FA is an accommodation.

I would argue that there's already an HTML way to solve this problem, and that's the html abbr element with the title attribute.

#a11y #html

: The Abbreviation element - HTML: HyperText Markup Language | MDN

The HTML element represents an abbreviation or acronym.

^{developer.mozilla.org}

Ensuring negative numbers are available for everyone. "The minus character (−) yields great support in most screen readers, and suffers less situational gotchas than the hyphen-minus character"

deque.com/blog/ensuring-negati…

Great article written by 2 of my favorite comrades.

#webdev #webdesign #a11y #html #tips #screenreaders

"Making a positive change: PDF to HTML
The Government Digital Service (GDS) states “Compared with HTML content, information published in a PDF is harder to find, use and maintain”."

Consider the needs of the people you are publishing the information for. Engage with them early to explore alternative options that may better meet their needs.

YES !

accessibility.blog.gov.uk/2023…

#PDF #HTML #A11Y #UX

Making a positive change: PDF to HTML

This is for everyone: documenting how we rebuild inclusive digital services across government

^{accessibility.blog.gov.uk}

The abbreviation appreciation society
“the HTML <abbr> element is deceptively familiar and attractive, its been around forever (1999) and thus people assume that it does what it does and does it well. Nothing much changed over the iterations of the abbr element definition over the years. One notable exception is that the acronym element was obsoleted in HTML5 and abbr now is used for both acronyms and abbreviations.”

#HTML #accessibility #WebDev

tpgi.com/short-note-the-abbrev…

/cc @micmath

Short note: The abbreviation appreciation society - TPGi

The HTML element is an incredibly common, but do you know how you can make it accessible? Find out how in this article.

^{Steve Faulkner (TPGi)}

Today the <blink> element was officially removed from MDN.

github.com/mdn/content/pull/26…

It was an awful element, but, oh, so many memories.

#HTML

Remove docs for the element by Elchi3 · Pull Request #26904 · mdn/content

For mdn/browser-compat-data#19658

^GitHub

#Development #Outlooks
The end of front-end development · Things are going to change, but not in the scary way people are saying ilo.im/11t8v2

_____
#Job #AI #GPT4 #ChatGPT #ChatBot #WebDevelopment #WebDev #Code #Frontend #HTML #CSS #JavaScript #Skills #Productivity

The End of Front-End Development

Large language models like GPT-4 are becoming increasingly capable, at an alarming rate. Within a couple of years, we won't need developers any more! …Or at least, that's the narrative going viral on Twitter.

^ilo.im

I have started contributing PR's to improve the @w3c #HTML Validator/Checker, you should too!

#WebDev #WebStandards

github.com/validator/validator…

Issues · validator/validator

Nu Html Checker – Helps you catch problems in your HTML/CSS/SVG - Issues · validator/validator

^GitHub

Glad <dialog> focus is finally being implemented/defined in a reasonable way after a torturous years long, largely pointless, discussion.

“1. Make the dialog focusing steps look at sequentially focusable elements instead of any focusable element.

2. Make the dialog element itself get focus if it has the autofocus="" attribute set.

3. Make the dialog element itself get focus as a fallback instead of focus being reset to the body element.”

#HTML #WebStandards #a11y

github.com/whatwg/html/commit/…

Implement dialog initial focus proposal · whatwg/html@a9f103c

This implements the changes proposed here: https://github.com/whatwg/html/wiki/dialog--initial-focus,-a-proposal#dialog-draft-text Specifically: 1. Make the dialog focusing steps look at seq...

^GitHub