Picking up post #58: that is the part I would want checked first.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Picking up post #58: that is the part I would want checked first.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Coming back to post #68, because the follow-up matters more than the original answer.
Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
post #71 answers the question as asked. The question underneath it is different.
Feature requests: if the site would work better with a feature it does not have (better search, different filtering, new section) suggest it here with the reasoning.
Coming back to post #71, because the follow-up matters more than the original answer.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Second pass at: The topic list is dense — is that deliberate?
Second pass at: The topic list is dense — is that deliberate? I have a specific reason for asking rather than idle curiosity, and the context is below. Nominating something for promotion into the…
|
+102 | 108 | 8.4k | 4mo |
|
Tag proliferation and whether we should prune
On the subject in the title: Tag proliferation and whether we should prune Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and the trust-level…
|
2 | 11k | 11mo | |
|
Mobile reading experience on long topics
Mobile reading experience on long topics Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the documentation commons. The topic in…
|
2 | 14k | 4h | |
|
Follow-up: Search filters: what is missing
On the subject in the title: Search filters: what is missing Working notes rather than a conclusion. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
+126 | 141 | 1.6k | 29d |
|
Tag proliferation and whether we should prune — what changed since
Tag proliferation and whether we should prune — what changed since — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The…
|
+5 | 9 | 709 | 5mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Request: export my own posts — one year on
Request: export my own posts — one year on — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps…
|
+66 | 70 | 14k | 4mo |
|
Revisiting: Sample size in a voluntary survey: the selection problem
Revisiting: Sample size in a voluntary survey: the selection problem — setting out what I have, and where I think it stops being reliable. Posting the method first, because I know what the first three replies…
|
2 | 56k | 9mo | |
|
Revisiting: Mobile reading experience on long topics
Posting this under the heading it deserves: Revisiting: Mobile reading experience on long topics Everything below is what sits behind that. Nominating something for promotion into the documentation commons.…
|
+11 | 15 | 34k | 10h |
|
Follow-up: Why we hide unevidenced fraud accusations and log the hiding
The question in the title: Why we hide unevidenced fraud accusations and log the hiding I will give what I have already checked below so nobody repeats it. Structured report rather than an opinion, following…
|
+12 | 16 | 17k | 12mo |
|
Maintainer handover: how it works
On the subject in the title: Maintainer handover: how it works Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and the trust-level page and I…
|
+76 | 82 | 14k | 16mo |