Index
Subject
: [lug] Digest (5 messages)
From
: lug-owner@lists.ncsu.[redacted]
Date
: Sun, 27 Sep 2015 13:27:58 -0400
The Lug Digest
Volume 1 : Issue 354 : "text" Format
Messages in this Issue:
201509/23 : PhreakNIC 19
PhreakNIC 19 <phreaknicburner@gmail.[redacted]>
201509/24 : Re: Making Clickable web elements Keyboard Accessible.
Jeffery Mewtamer <mewtamer@gmail.[redacted]>
201509/25 : Re: Making Clickable web elements Keyboard Accessible.
Quentin Young <qlyoung@ncsu.[redacted]>
201509/26 : Re: Making Clickable web elements Keyboard Accessible.
Jeffery Mewtamer <mewtamer@gmail.[redacted]>
201509/27 : Automating Metaflac
Jeffery Mewtamer <mewtamer@gmail.[redacted]>
----------------------------------------------------------------------
Date: Tue, 22 Sep 2015 00:16:37 -0500
From: PhreakNIC 19 <phreaknicburner@gmail.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: PhreakNIC 19
Message-ID: <5600E435.7040507@gmail.[redacted]>
Fall is almost upon us. The air is getting cooler, the leaves are
starting to change colors, and the birds are beginning to fly south.
That means just one thing:
PhreakNIC is coming.
PhreakNIC is one of the oldest non-profit hacker cons in the country,
organized by Nashville 2600 and held annually since 1997 in the
Nashville, TN area. This year we're back at the Clarion Inn and Suites
in Murfreesboro, TN on November 6th and 7th. If you're interested in
attending, more info can be found at http://phreaknic.info.
This year we're offering a good mixture of speakers, from Elonka Dunin's
talk about the Beale Ciphers to Thomas Flatt's talk about his book, The
Eleven-Year-Old's Guide to Linux. Those speakers and more can be read
about at the following links:
http://phreaknic.info/speaker.html
http://phreaknic.info/sessions.html
If you want to do something else at the con, we have other activites
planned, such as the return of Network King of the Hill, more
traditional gaming (Including but not limited to benthemeek's Unreal 99
port-a-LAN), and plans to play board games such as Settlers of Catan and
Cards Against Humanity. Here are some of the extra activities we have
planned:
http://phreaknic.info/activities.html
Want to do more than just attend? Your options range from volunteering
to help us put the con on, to doing a presentation, to being a vendor or
a sponsor. The info you need can be found at the following links:
http://phreaknic.info/speak.html
http://phreaknic.info/volunteers.html
http://phreaknic.info/sponsor.html
http://phreaknic.info/vendors.html
Obligatory social media:
https://twitter.com/phreaknic
https://twitter.com/nashville2600
https://facebook.com/nashville2600
------------------------------
Date: Tue, 22 Sep 2015 08:33:30 +0000
From: Jeffery Mewtamer <mewtamer@gmail.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Making Clickable web elements Keyboard Accessible.
Message-ID: <CAO2sX3189S4TdBMrXM9UPNB5Bmz7BwLi2QVNXsmJD8GB=ecmHQ@mail.gmail.[redacted]>
Sorry for not thinking to include an example of a page showing the problem.
Here's the page that pushed me from finding it an easily ignored
inconvenience to wanting to find a solution:
https://www.zintellect.com/Account/Register
On the linked page, the offending element is the register link(tabbing
jumps straight from cancel to help).
Okay, just thought to do an experiment: I don't know if the function
is part of Iceweasel/Firefox or an accessibility feature added by
Orca, but pressing various buttons on my keyboard will cause my cursor
to jump between page elements of a given type. Normally, I just use
h(for headings at all levels) 1-6(for headings at specific levels) and
t(for tables) for quickly navigating pages, but it turns out that
there is such a shortcut for clickables(the a key). This should mean I
now have a way of putting focus on a clickable and just need a way to
activate them without a mouse(though clicking my laptop's touchpad
might work if I reinstall xserver-input-mouse, but then I have to
worry about the noise generated when accidental contact is made with
the touchpad).
On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
> Hi Jeffery,
>
> Can you possibly link me to a webpage exhibiting this behavior? I haven't
> found anything existing that fits your needs but I have an idea for an easy
> implementation.
>
> Quentin
>
> On Mon, Sep 21, 2015 at 6:37 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
> wrote:
>
>> Good morning,
>>
>> I use Iceweasel/Firefox in combination with the Orca screenreader for
>> browsing the Internet, and there's one bit of bad web design that
>> keeps rearing its ugly head: Buttons and other web controls that orca
>> identifies as being clickable. I can't use a mouse, they get skipped
>> over when tabbing between links and form elements, and the enter and
>> space keys do nothing if I manually position the cursor on them.
>> Google would indicate that this is a fairly well known problem in the
>> area of web accessibility, but every fix I've found via Google has
>> been targeted at web designers who want the greater visual flexibility
>> such elements allow without rendering their pages unusable to screen
>> reader users. I've been unable to find anything that assists with
>> making these elements accessible on the end-user side of things.
>>
>> Anyone have any suggestions for possible solutions?incerely,
>>
>> Jeffery Wright
>> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>> Former Secretary, Student Government Association, College of the
>> Albemarle.
>>
>
>
>
> --
> Quentin Young
> Vice President, LUG @ NC State
>
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
------------------------------
Date: Tue, 22 Sep 2015 15:02:19 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Making Clickable web elements Keyboard Accessible.
Message-ID: <CANhSzx11Nnc-JjW2nSrG20gXEZtQvpVY-rL3aoFsmta0xP2s9Q@mail.gmail.[redacted]>
I was looking through the Orca documentation last night and it appears that
using 'a' to select clickable elements is functionality provided by Orca.
If 'a' puts focus on the clickable element, you should be able to activate
the element with the enter key, correct? Am I misunderstanding?
If that doesn't work, I have a different solution, although it is something
of a hack. On the page you linked, by inserting a tab index attribute on
the register button element using the browser's html editor, the browser
will allow you to tab onto the button as you normally would.
It would probably be pretty easy to write a grease monkey script, or
something similar, that simply adds a tab index to each element on the
page, to make sure that all elements can be tabbed to. If you're interested
in that I would be happy to play with the idea and see what I can come up
with.
Quentin
On Tue, Sep 22, 2015 at 4:33 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
wrote:
> Sorry for not thinking to include an example of a page showing the problem.
>
> Here's the page that pushed me from finding it an easily ignored
> inconvenience to wanting to find a solution:
> https://www.zintellect.com/Account/Register
>
> On the linked page, the offending element is the register link(tabbing
> jumps straight from cancel to help).
>
> Okay, just thought to do an experiment: I don't know if the function
> is part of Iceweasel/Firefox or an accessibility feature added by
> Orca, but pressing various buttons on my keyboard will cause my cursor
> to jump between page elements of a given type. Normally, I just use
> h(for headings at all levels) 1-6(for headings at specific levels) and
> t(for tables) for quickly navigating pages, but it turns out that
> there is such a shortcut for clickables(the a key). This should mean I
> now have a way of putting focus on a clickable and just need a way to
> activate them without a mouse(though clicking my laptop's touchpad
> might work if I reinstall xserver-input-mouse, but then I have to
> worry about the noise generated when accidental contact is made with
> the touchpad).
>
> On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
> > Hi Jeffery,
> >
> > Can you possibly link me to a webpage exhibiting this behavior? I haven't
> > found anything existing that fits your needs but I have an idea for an
> easy
> > implementation.
> >
> > Quentin
> >
> > On Mon, Sep 21, 2015 at 6:37 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
> > wrote:
> >
> >> Good morning,
> >>
> >> I use Iceweasel/Firefox in combination with the Orca screenreader for
> >> browsing the Internet, and there's one bit of bad web design that
> >> keeps rearing its ugly head: Buttons and other web controls that orca
> >> identifies as being clickable. I can't use a mouse, they get skipped
> >> over when tabbing between links and form elements, and the enter and
> >> space keys do nothing if I manually position the cursor on them.
> >> Google would indicate that this is a fairly well known problem in the
> >> area of web accessibility, but every fix I've found via Google has
> >> been targeted at web designers who want the greater visual flexibility
> >> such elements allow without rendering their pages unusable to screen
> >> reader users. I've been unable to find anything that assists with
> >> making these elements accessible on the end-user side of things.
> >>
> >> Anyone have any suggestions for possible solutions?incerely,
> >>
> >> Jeffery Wright
> >> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
> >> Former Secretary, Student Government Association, College of the
> >> Albemarle.
> >>
> >
> >
> >
> > --
> > Quentin Young
> > Vice President, LUG @ NC State
> >
>
>
> --
> Sincerely,
>
> Jeffery Wright
> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
> Former Secretary, Student Government Association, College of the Albemarle.
>
--
Quentin Young
Vice President, LUG @ NC State
[Attachment of type text/html removed.]
------------------------------
Date: Tue, 22 Sep 2015 19:39:00 +0000
From: Jeffery Mewtamer <mewtamer@gmail.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Making Clickable web elements Keyboard Accessible.
Message-ID: <CAO2sX30sMcgQL2zFXv_2-OXD+EwdRp-jzw0CGWq0+AL9Ex9B9A@mail.gmail.[redacted]>
My web coding knowledge doesn't cover anything more complex than
creating tables and simple forms in HTML and using PHP to display data
collected via an HTML form, but best I can gather from Google results,
making a clickable accessible requires setting not only a tab index to
allow it to gain focus with the tab key, but also a key press handler
to trigger the click via space/enter. Orca seems to compensate for the
lack of a tab index thanks to pressing a to jump between clickables,
but pressing space or enter after using a to gain focus does nothing,
even after ensuring that I've told NoScript to let everything on the
relevant page through(My main reason for using NoScript being that
most websites are easier for Orca to read when scripts are blocked).
On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
> I was looking through the Orca documentation last night and it appears that
> using 'a' to select clickable elements is functionality provided by Orca.
> If 'a' puts focus on the clickable element, you should be able to activate
> the element with the enter key, correct? Am I misunderstanding?
>
> If that doesn't work, I have a different solution, although it is something
> of a hack. On the page you linked, by inserting a tab index attribute on
> the register button element using the browser's html editor, the browser
> will allow you to tab onto the button as you normally would.
>
> It would probably be pretty easy to write a grease monkey script, or
> something similar, that simply adds a tab index to each element on the
> page, to make sure that all elements can be tabbed to. If you're interested
> in that I would be happy to play with the idea and see what I can come up
> with.
>
> Quentin
>
> On Tue, Sep 22, 2015 at 4:33 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
> wrote:
>
>> Sorry for not thinking to include an example of a page showing the
>> problem.
>>
>> Here's the page that pushed me from finding it an easily ignored
>> inconvenience to wanting to find a solution:
>> https://www.zintellect.com/Account/Register
>>
>> On the linked page, the offending element is the register link(tabbing
>> jumps straight from cancel to help).
>>
>> Okay, just thought to do an experiment: I don't know if the function
>> is part of Iceweasel/Firefox or an accessibility feature added by
>> Orca, but pressing various buttons on my keyboard will cause my cursor
>> to jump between page elements of a given type. Normally, I just use
>> h(for headings at all levels) 1-6(for headings at specific levels) and
>> t(for tables) for quickly navigating pages, but it turns out that
>> there is such a shortcut for clickables(the a key). This should mean I
>> now have a way of putting focus on a clickable and just need a way to
>> activate them without a mouse(though clicking my laptop's touchpad
>> might work if I reinstall xserver-input-mouse, but then I have to
>> worry about the noise generated when accidental contact is made with
>> the touchpad).
>>
>> On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>> > Hi Jeffery,
>> >
>> > Can you possibly link me to a webpage exhibiting this behavior? I
>> > haven't
>> > found anything existing that fits your needs but I have an idea for an
>> easy
>> > implementation.
>> >
>> > Quentin
>> >
>> > On Mon, Sep 21, 2015 at 6:37 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
>> > wrote:
>> >
>> >> Good morning,
>> >>
>> >> I use Iceweasel/Firefox in combination with the Orca screenreader for
>> >> browsing the Internet, and there's one bit of bad web design that
>> >> keeps rearing its ugly head: Buttons and other web controls that orca
>> >> identifies as being clickable. I can't use a mouse, they get skipped
>> >> over when tabbing between links and form elements, and the enter and
>> >> space keys do nothing if I manually position the cursor on them.
>> >> Google would indicate that this is a fairly well known problem in the
>> >> area of web accessibility, but every fix I've found via Google has
>> >> been targeted at web designers who want the greater visual flexibility
>> >> such elements allow without rendering their pages unusable to screen
>> >> reader users. I've been unable to find anything that assists with
>> >> making these elements accessible on the end-user side of things.
>> >>
>> >> Anyone have any suggestions for possible solutions?incerely,
>> >>
>> >> Jeffery Wright
>> >> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>> >> Former Secretary, Student Government Association, College of the
>> >> Albemarle.
>> >>
>> >
>> >
>> >
>> > --
>> > Quentin Young
>> > Vice President, LUG @ NC State
>> >
>>
>>
>> --
>> Sincerely,
>>
>> Jeffery Wright
>> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>> Former Secretary, Student Government Association, College of the
>> Albemarle.
>>
>
>
>
> --
> Quentin Young
> Vice President, LUG @ NC State
>
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
------------------------------
Date: Sun, 27 Sep 2015 15:07:42 +0000
From: Jeffery Mewtamer <mewtamer@gmail.[redacted]>
To: lug <lug@lists.ncsu.[redacted]>
Subject: Automating Metaflac
Message-ID: <CAO2sX30QO5=8Xp7vekDFKkbp3K0doR5+yZJYc8jCcxLwdMpwBw@mail.gmail.[redacted]>
Recently, I've started amassing a Library of Audiobooks in Audio CD
format and ripping them to flac with abcde as I've been doing with
music CDs for years. However, I've run into a few snags from an
organizational standpoint.
Ideally, I want one chapter per file with each file having the
following path anf filename:
~/Library/Author Name/Book Title/## Chapter Title.flac
With each file having the following tags:
Artist=Author Name
Album=Book Title
Title= Chapter Title
Track= Chapter Number
Sox provides an elegant solution for Books-on-CD that have multiple
tracks per chapter, and the only real issue I'm having with file names
is that abcde uses underscores in filenames and I prefer spaces, at
least when a disc has a CDDB hit and I only have to change track
number to chapter number.
Where I'm having problems is with tags. I've figured out enough about
metaflac to make a script to tag an entire book worth of files as well
as a second script to generate a list of Chapter Titles and file names
to plug into the metaflac script(it does rely on the files already
being appropriately named), but there's still a lot of cutting and
pasting for each book I tag in this way.
Any suggestions on how I could further automate the process? In
addition to the script with spaces for file names and chapter
titles(tag.sh) and the script that I made for generating a list of
chapter titles and file names(file_list.sh) I've included the complete
scripts for the two books I've already tagged in this way.
Also, if anyone know of any command line tools that could assist in
any of the following it would be appreciated:
Recursively scanning a dirctory and replacing all _ in filenames with spaces.
Assisting with transliterating non-latin(primarily Japanese) filenames
to a Latin character set.
Transliterating non-Latin tags in flac files to a latin character
set(again, primarily dealing with Japanese-to-Latin Alphabet)..
[Attachment of type application/x-sh removed.]
[Attachment of type application/x-sh removed.]
[Attachment of type application/x-sh removed.]
[Attachment of type application/x-sh removed.]
------------------------------
End of [lug] Digest (5 messages)
**********