Native built-in browser elements you can use today instead of ARIA or ROLE attributesArticle contains
  1. The first rule of ARIA
  2. Why move away from ARIA?
    1. Browser-engine privilege
    2. Less code, less maintenance
    3. Smaller payload, faster render
    4. Built-in resilience to future spec changes
    5. Mobile and voice-input compatibility
    6. Security and performance isolation
    7. Internationalisation for free
    8. Future-proofing for new input modalities
    9. Easier testing and audits
    10. Legal, procurement safety
  3. When ARIA is still justified
  4. Native HTML replacements for ARIA roles and attributes
  5. Conclusion
Text "Aria to semantic HTML" where "HTML" is on tiles.

Native built-in browser elements you can use today instead of ARIA or ROLE attributes

When building accessible web applications, developers have long relied on ARIA and role attributes to fill gaps in native HTML.

But today, many of those gaps are gone. Modern browsers support a wide range of semantic HTML elements and built-in behaviors that make ARIA redundant in most cases, often with better results and fewer bugs.

This shift towards native accessibility features means that developers can now create accessible web applications using built-in browser elements and attributes, rather than relying solely on ARIA and ROLE only.

We’ll explore the native built-in browser elements and attributes that you can use today to improve accessibility, and how they can replace or complement ARIA and ROLE attributes in your web development workflow. By leveraging these native features, you can simplify your code, improve maintainability, and create more accessible web applications for everyone.

Continue reading “Native built-in browser elements you can use today instead of ARIA or ROLE attributes”
Semantic HTML explainedArticle contains
  1. What is semantic in HTML?
  2. What is the difference between semantic HTML and traditional HTML?
    1. Traditional HTML
    2. Semantic HTML
  3. Key differences
  4. What is an example of a semantic code?
  5. Benefits of semantic HTML
  6. What is semantic HTML in accessibility?
    1. Meaningful structure for assistive technologies
    2. Improved content understanding
    3. Enhanced keyboard navigation
    4. Compatibility with ARIA attributes
  7. Does semantic HTML improve SEO?
    1. Better content structure
    2. Enhanced crawling and indexing
    3. Rich snippets and featured results
    4. Keyword context
  8. Semantic HTML enhances maintainability and code readability
  9. Web components
  10. Challenges and traps
  11. Considerations and best practices
    1. Structured data (JSON-LD)
    2. Using ARIA and role attributes
  12. Frequently asked questions
    1. Why should I use semantic HTML?
    2. Why should I worry about semantic HTML when I use structured data (JSON-LD)?
  13. Summary
Four tiles and on each of them letters: H, T, M, L. Above sentence: semantic. Image by Miguel Á. Padriñán from Pixabay

Semantic HTML explained

Semantic HTML. The term itself might sound technical and niche, but its impact on the web is anything but. It’s the foundation upon which accessible, maintainable, and search engine-friendly website content is built. Let’s dive into the core principles of semantic HTML, exploring its benefits, common pitfalls, and ultimately, why it’s a crucial skill for any web developer.

Continue reading “Semantic HTML explained”
Should we avoid writing in all caps?Article contains
  1. Uppercase text slows down reading speed
  2. The effect of uppercase text on word recognition
  3. Why all caps are perceived as yelling
  4. Alternatives to using all caps for emphasis
    1. Use italics for emphasis
    2. Use bold formatting
    3. Small caps
    4. Employ strategic placement and punctuation
    5. Avoid overemphasis
  5. Does all caps affect screen readers?
  6. English capitalization guidelines
  7. Does capitalization affect SEO?
  8. Are there any legal requirements or regulations regarding the use of all caps in digital communications?
  9. Conclusion
Sentence "FRAGILE" on the wood written in all caps

Should we avoid writing in all caps?

Uppercase reading is more difficult to read since the forms of all uppercase letters are rectangular, and readers are not used to reading text in this way. As a result, it is more difficult to scan, less efficient, and hence less readable.

However, all caps are accepted for words that do not need reading, such as logos and acronyms.

One of the simplest methods to improve your website’s content is to use consistent capitalization guidelines. Above all, do not use all capital letters (commonly known as all caps) in your headings and text.

Continue reading “Should we avoid writing in all caps?”
Best practices for optimizing SVG codeArticle contains
  1. Minify the code
  2. Compress the SVG files
    1. Enabling serving SVGZ files in Apache
    2. Enabling serving SVGZ files in Nginx
    3. Enabling serving SVGZ files in IIS
    4. Example page with SVG and SVGz
  3. Using Inkscape to create optimized SVGs directly
  4. Command-line tool using SVGO NPM package
Check if a string is valid HTML using JavaScriptArticle contains
  1. Key considerations
  2. Essential requirements
  3. How does the DOMParser interface parse HTML strings differently based on the mimeType argument?
  4. Practical example
  5. Code
  6. Example of validation error
  7. What a MIME type is and why it's used in the isStringValidHtml function?
  8. How does the DOMParser API handle invalid HTML syntax?
  9. How can you ensure that HTML string validation in JavaScript correctly detects missing or misplaced tags?
    1. 1. Mechanical check - is every tag balanced?
    2. 2. Semantic check - did the browser mutate the DOM?
    3. 3. One-line validator
    4. 4. Server-side (Node.js) usage
  10. Summary
Keyboard with all empty keys except four keys: H, T, M, and L next to each other.

Check if a string is valid HTML using JavaScript

There isn’t a single definitive way to determine if a string is valid HTML, as HTML itself is flexible and can be malformed. However, we can use various methods to check for the presence of HTML-like structures in a string.

One method is to use DOMParser API and its method parseFromString.

The DOMParser API interface allows you to parse XML or HTML source code from a string and convert it into a DOM Document. It is used to convert a string of XML or HTML into a structured DOM object that can be easily manipulated using JavaScript.

Continue reading “Check if a string is valid HTML using JavaScript”
Designing for dyslexic usersArticle contains
  1. What actually is dyslexia?
  2. Designing for dyslexia as a key to inclusivity and accessibility
  3. Choose clear fonts and typography
  4. Format text for ease of reading
  5. Use high contrast colors
  6. Incorporate multimedia for visual aids
  7. Use simple language and writing style
  8. Design intuitive navigation and layout
  9. Using images and diagrams to support text
  10. Additional resources related to designing for dyslexic users
  11. Summary of key points
A person on the background of a puzzle

Designing for dyslexic users

Did you know that optimizing your digital content for dyslexic users may not only boost your website’s accessibility but also increase your customer base? With an estimated one out of ten people having dyslexia, that’s roughly 780 million people worldwide (1 out of 10 people have dyslexia) who could benefit from dyslexia-friendly design.

Dyslexia is a specific learning disability characterized by difficulties with accurate and/or fluent word recognition and poor spelling and decoding abilities. To ensure that your content is inclusive and accessible, consider implementing certain design considerations.

Continue reading “Designing for dyslexic users”
How do you measure the success of the website project?Article contains
  1. Key points of measuring the success of the website project
  2. What metrics and analytics do you use to track and report the website's performance and impact?
  3. Can data-driven decisions really optimize my website's user experience, content, and marketing strategies?
Font Italics: Improving Accessibility with Best PracticesArticle contains
  1. Are italic fonts always inaccessible?
  2. The impact of italic fonts on web accessibility
  3. Comparing three font families for readability: OpenDyslexic 3, Arial, and Tahoma
  4. Best practices for using italic fonts in web accessibility
  5. A summary of italic fonts and web accessibility
Hiding a text but making it accessible to a screen readerArticle contains
  1. Making hidden text accessible to screen readers: a guide
    1. Notes
  2. Difference between CSS class .visually-hidden and .sr-only
  3. Accessibility and Hidden Text: Can Screen Readers Detect It?
  4. How visibility: hidden affects screen readers
  5. Is there a way to test whether the hidden text is actually being read by screen readers after applying the .visually-hidden class?
  6. Why hide text from sighted users?
Female eye-looking, peeking through a triangle blue background

Hiding a text but making it accessible to a screen reader

Accessible hiding allows an element to be visually hidden while remaining accessible to assistive technologies such as screen readers. The approach is to apply a CSS class to the element that should not be shown.

There are several solutions for this type of CSS class, but we recommend following styles that cover hiding elements and optionally giving the ability to show the element when the element receives the focus or contains an element that has received focus. Useful for Skip to the main content links. See Adding a link at the top of each page that goes directly to the main content area.

Continue reading “Hiding a text but making it accessible to a screen reader”
The key to agile accessibility: effective measurement of what mattersArticle contains
  1. Why should you track the performance of your agile accessibility efforts?
  2. What should you track to see if your agile approach to accessibility is effective?
  3. What are some common myths about accessibility in agile development?
Software testing. Two persons with multiple devices.

The key to agile accessibility: effective measurement of what matters

Agile accessibility is the incorporation of accessibility principles and practices into the agile software development methodology.

Ensuring accessibility is a constant and iterative process throughout the development cycle, meaning making sure that software and web applications are designed and developed with accessibility in mind from the very beginning.

Tracking accessibility KPIs is a critical step in ensuring that your digital products are accessible to all users.

Continue reading “The key to agile accessibility: effective measurement of what matters”