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.
-
an example of "code-like" but non-code items using equal space font available from code block feature in this post space.stackexchange.com/a/61186/12102 that could be reviewed by folks skilled and experienced in the use of screen readers– uhohCommented Dec 7, 2022 at 4:13
-
see also How can I find posts with particularly large code blocks in a non-code-based site?– uhohCommented Dec 7, 2022 at 8:37
-
7This is something that should be a paid position, not something that SE should unload to the community. Editing guidance notwithstanding needs to be stronger on the "avoid formatting as much as possible"– BraiamCommented Dec 8, 2022 at 0:20
-
1@Braiam I wholeheartedly agree that a website as impactful as this should already have either a paid position, or at a minimum retain expert consolation services so that it maximizes its accessibility. But in addition to that there is a lot of community interest in developing some "best practices" and guidelines for how to use the site's features. These are two separate things, and what I propose here would not be "unloading" nor a release of SE from their responsibilities. Just the opposite; community feedback about accessibility can foster more accountability. It's not an either/or thing– uhohCommented Dec 8, 2022 at 0:48
-
1@Braiam See again the answer post I've linked to in my first comment, an SE staff is not the right person to decide if a) a code block or SE table is the best way to display JPL Horizions output whose formatting depends on equal paced font and benefits from those horizontal and vertical sliders, that's a community decision. Arguments against the code block display go back to a 10 year old MSE answer about using the back ticks in comments for emphasis. Q: How does that formatting in posts get processed by screen readers vs SE tables? Why would you vote against community input on that?– uhohCommented Dec 8, 2022 at 0:55
Add a comment
|
How to Edit
- 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
How to Format
-
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**
- indent code by 4 spaces
- backtick escapes
`like _so_`
- 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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you