@linuxlawson, my choice is deliberate:

Pedro
GitHub Support
Pedro commented 11 days ago

Hi BEEDELLROKEJULIANLOCKHART,
Let me help you out here! It seems that changing the "README" file extension from .txt to .md would solve the issue.
Also, could you expand on your use case for using a .txt extension for your "README" file?

BEEDELLROKEJULIANLOCKHART commented 11 days ago
I am thankful for your response and suggested solution.

However, my use-case is that I specifically do not want any of the text of the file to be interpreted as Markdown, because conversion to Markdown would cause me to lose much of my ability to format my read-me. (If you copy the file to a repository and rename it to .md rather than .txt, you shall observe what I refer to.)

However, even if my rationale were better served by Markdown, I believe that this feature would be beneficial for others, because I see no good reason for the read-me view to provide fewer accessibility features than the editor, considering that the former is probably more frequently observed than the latter.

Pedro commented 11 days ago
Your ticket was automatically routed to our GitHub Support team, but our Product team is better suited to help you out. I've passed this information on to the product team for future consideration.

For future reference, the best way to report any feature requests or feedback is directly through our feedback form:
Share feedback

(That is a modified transcript of "https://support.github.com/ticket/personal/0/1706221".)

@BEEDELLROKEJULIANLOCKHART Thanks for the feedback. I'm interested to understand how you are defining accessibility. The feature idea you have makes sense but I think it's more of a presentation preference than an accessibility issue.

I'm defining accessibility as "an issue which has an impact on people with disabilities".

• Can you help me understand how you're defining accessibility?
• If we share the same definition, can you help me make the connection between this feature request and accessibility?

@benjiallen, for some, larger indents are much more easy to visually process than smaller ones. That is noticeably not true for me, but definitely is for my father, whose sight is not brilliant. This means that his documentation uses spaces usually because of unfortunate lack of support via services such as GitHub for configurable indentation-width.

@BEEDELLROKEJULIANLOCKHART have you had any luck configuring tab size using the appearance settings?

Docs for appearance settings.

@benjiallen, no. Have you somehow?