Hi
user
Admin Login:
Username:
Password:
Name:
Thanks for maintaining a desktop environment. But is it accessible?
--client
debian
--show
debconf15
--room Heidelberg 10192 --force
Next: 1 Packaging the free software web for the end user
show more...
Marks
Author(s):
Samuel Thibault
Location
Heidelberg
Date
aug Sat 22
Days Raw Files
Start
11:00
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
11:45
Last Raw End
Chapters
Total cuts_time
None min.
https://summit.debconf.org/debconf15/meeting/290/thanks-for-maintaining-a-desktop-environment-but-is-it-accessible/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Thanks_for_maintaining_a_desktop_environment_But_is_it_accessible.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
The graal of accessibility is that it should be ready to be enabled everywhere, all the time. Some of the Debian desktops are very accessible, but most of them are not. In this talk, I will present how the accessibility stack is packaged in Debian, how it works, and what desktop maintainers need to do to make sure that their desktop is accessible.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review