h a l f b a k e r y
Please listen carefully, as our opinions have changed.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
or get an account
In regards to searching for codes randomly in a notepad,
this is easy for a normal sighted person to do, for the
it may take longer.
Perhaps to improve random seek time when using a
reader on source codes, we can study how the human
scan codes when seeking.
way I think people perceive when scanning. Is that
they already know what the code looks light roughly.
Which means they are looking to recognise a line of code
as the end condition. (Thus you would sped the speaking
speed by x3, as we are less about readability and more
Hmmm... also people scanning speed is variable. You
very fast, then you get the general areas, then you
for the specific line.
Which means you would have 3 speed settings. One
jumps entire sections (focusing on reading major
comments). The second which jumps between
parentheses. And the last one that scans between lines.
(Logic depends on outcome of studies of how people
actually randomly seek for a line of text)
<<<Sections | << Blocks | < Lines > | Blocks>> |
tl;dr edit: The idea is basically, to make "jump searching"
via screen reader to be a little smarter, by actually
analysing the text structure.
Original Comment Reddit (Posted by mofosyne)
[mofosyne, Jan 30 2015]
Please log in.
If you're not logged in,
you can see what this page
looks like, but you will
not be able to add anything.
Description (displayed with the short name and URL.)
||Well, I'm wondering if there is an equivalent to "flipping the
page, and quickly looking for a topic of interest" for "text to
speech" screen readers.
||One that can do well perhaps in searching for a line of code
(that you don't remember exactly). And also perhaps for
other things like flipping though a newspaper.
||Oh. You could have said so. Good luck with your homework :-)
||The solution is conceptually pretty easy, though parsing source code for some unmentioned reason (debugging somebody else's stuff ?) would be pretty clunky. But plain old text would be a snap.
||Well conceptually it's easy to understand. Only issue is
finding the right settings and algorithm, and getting it
blind people who are as blind as a bat (and see if it
||And even if you do get it working... it would require more
work on applications developers to make their stuff
accessible (can't just expose the text... need to make it
dynamically searchable, and self descriptive too D: ) It's
already hard to get them to label their buttons properly.
||Yes, but, to the point, you haven't posted an Idea and you're trying to make us go look to find out what you're going on about.
||Eh, I don't remember seeing this particular concept
anywhere. This post is the idea.
||The idea is basically, to make "jump searching" via screen
reader to be a little smarter, by actually analysing the
||Perhaps this is not well explained. If so then, I can try
rewriting it again more concisely. (Oh and btw "Original
Comment" is actually my post. Link edited to make it
||Try googling for ' "programming editor" for the blind ' . Some of the results look promising. Another useful string might be " blind 'text editor' features " or something like that.