Edit - User Experience Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Great - thanks for the info about screen readers, and also for the point about 508 and WCAG. I think you and Andrew both have answered my question: this requirement is about structure and order, and not about a css-free browsing experience. Our structure and order are good and markup is mostly semantic (working on replacing legacy bits like click-handled spans...). For planning purposes, we should concern ourselves with the accessibility of UI widgets but not with their appearance when css is disabled. I'm selecting this as the best answer for good summary and bonus info about screen readers.

aames
– aames

2015-07-30 14:01:44 +00:00
Commented Jul 30, 2015 at 14:01

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »