Search

Items tagged with: HTML


This is an interesting #HTML proposal from @Seirdy

Should there be a `<spoiler>` element?

seirdy.one/posts/2023/11/12/sp…

My heart says yes. HTML should reflect what people are actually doing on the web. How they write. The features they invent.

But my head says it is a duplicate of `<details>` albeit non-block level.



"Most importantly, tooltips should only provide descriptive and non-essential text, giving slightly more detailed text for active elements such as links and form controls. Ultimately, they provide expendable text which is already on the web page."

htmhell.dev/adventcalendar/202…

Great in-depth article about #tooltips by Jan Hellbusch. He knows what he's talking about, had the pleasure to be in one of his workshops and he's an absolute pro. 🤯

#HTML #CSS #JavaScript #accessibility #a11y #HTMHell



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







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



"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

#a11y #html #UX #pdf


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




#html










I find that web developers need to implement inputmode more often (to customize virtual keyboard for phone, email, etc). Hey Safari, why don't you support it?! developer.mozilla.org/en-US/do… #safari #browsers #html #forms #usability