3 ms·

This was a problem years ago. however, nowadays almost all screen readers have a setting to report the indentation of the current line. This was popularized whe

This was a problem years ago. however, nowadays almost all screen readers have a setting to report the indentation of the current line. This was popularized when NVDA (a Windows screen reader) and Orca (a screen reader for Linux) were written, since they are both in Python.

tetraodonpuffer 11y ago
thanks for chiming in, I was really wondering about it btw, if you read this, do you have any recommendations for ways we can make sure our sites are accessible? Say for my blog I have alt= tags for everything and tried to organize things meaningfully in terms of H tags, I would like to also add aria tags but I am not sure how I can check that they were done correctly, as even if I installed a screen reader it I don't have any experience with it so I am not sure if what I hear is correct or not. Do you have any suggestions?
- mwcampbell 11y ago
  (Not the OP, but I have experience in this area too.) You're on the right track. As a finishing touch, you should add role="main" to whichever element contains the main page content (in this case, the article or the most recent articles). That way, screen reader users can easily skip past all the navigation links and other auxiliary elements that are common to every page.
  - tetraodonpuffer 11y ago
    thanks for the tip!
    - parham90 11y ago
      Sorry for being late to this thread. You can also use some accessibility evaluation tools. I would suggest that you go here, and check the box that says "WCAG 2.0" to get some tools that check accessibility in general: http://www.w3.org/WAI/ER/tools/ http://www.w3.org/WAI/ER/tools/ If you fix stuff that these evaluation software show you, I think your blog will be among the very well thought-out websites in terms of accessibility. WAI-ARIA is for times that your application does a lot with Javascript, such as updating a region of text, or when you start using non-semantic elements for stuff they are not meant for (for example using the i tag for an icon, or the span tag as a link, etc).
      - tetraodonpuffer 10y ago
        thanks for the extra information

tetraodonpuffer 11y ago

thanks for chiming in, I was really wondering about it btw, if you read this, do you have any recommendations for ways we can make sure our sites are accessible? Say for my blog I have alt= tags for everything and tried to organize things meaningfully in terms of H tags, I would like to also add aria tags but I am not sure how I can check that they were done correctly, as even if I installed a screen reader it I don't have any experience with it so I am not sure if what I hear is correct or not. Do you have any suggestions?

mwcampbell 11y ago
(Not the OP, but I have experience in this area too.) You're on the right track. As a finishing touch, you should add role="main" to whichever element contains the main page content (in this case, the article or the most recent articles). That way, screen reader users can easily skip past all the navigation links and other auxiliary elements that are common to every page.
- tetraodonpuffer 11y ago
  thanks for the tip!
  - parham90 11y ago
    Sorry for being late to this thread. You can also use some accessibility evaluation tools. I would suggest that you go here, and check the box that says "WCAG 2.0" to get some tools that check accessibility in general: http://www.w3.org/WAI/ER/tools/ http://www.w3.org/WAI/ER/tools/ If you fix stuff that these evaluation software show you, I think your blog will be among the very well thought-out websites in terms of accessibility. WAI-ARIA is for times that your application does a lot with Javascript, such as updating a region of text, or when you start using non-semantic elements for stuff they are not meant for (for example using the i tag for an icon, or the span tag as a link, etc).
    - tetraodonpuffer 10y ago
      thanks for the extra information