The cost of a movie ticket has increased dramatically over the last ten years, beating the consumer price index (used to measure inflation) be a considerable amount. One thing that theater owners and Hollywood is going to have to realize is that the market will no longer bear the $12 per ticket pricetag for often poorly made entertainment.
DVDs do provide a higher quality medium for distrubtion of movies than conventional VHS tapes, but thy do not replace the experience of going to the movies. Many people (myself included) enjoy an evening at the movie theatre, but I am unwilling to pay the exorbatant price tag for it. This is quite similar to the way I feel about golf. Great game. Not for $100.00 per afternoon. (Besides, why would anyone want to spend $100 to get pissed off, I can do that for free at home:)
In any event, I think that movies will be alive and well far into the future... as public demand for the physical theatre wains, prices will drop, actors salaries will go down, and people will return to the movies again.
What would be interesting is if an automated tool were developed specifically to convert sites to a 508 compliant standard (for those not in the Government, Section 508 details all the rules for creating an electronically accessable web site).
One major fault of developers is feeling that it is necessary to create one site that is usable by blindreaders such as Jaws and conventional browsers. For blindreaders to function properly, the site had to be downgraded to a circa 1996 architecture. This makes the site unpleasent and potentially less usable for the vast majority of non-disabled users. Ideally, a tool should be created that automatically looks at your site, and places the content in deadly dull plain text in a separate URL. This duplicate URL tree would be maintained automatically, and users could access it by clicking on a handicapped icon at the top of the screen.
As for other portions of disability developing (there are many of them), it is just good development practice to not rely on color to denote action (colorblind people have a horible time with redlight greenlight stuff). Small changes like that are just concious actions that the developer can make to make their user community more functional.
Slashdot Mirror
The cost of a movie ticket has increased dramatically over the last ten years, beating the consumer price index (used to measure inflation) be a considerable amount. One thing that theater owners and Hollywood is going to have to realize is that the market will no longer bear the $12 per ticket pricetag for often poorly made entertainment.
:)
DVDs do provide a higher quality medium for distrubtion of movies than conventional VHS tapes, but thy do not replace the experience of going to the movies. Many people (myself included) enjoy an evening at the movie theatre, but I am unwilling to pay the exorbatant price tag for it. This is quite similar to the way I feel about golf. Great game. Not for $100.00 per afternoon. (Besides, why would anyone want to spend $100 to get pissed off, I can do that for free at home
In any event, I think that movies will be alive and well far into the future... as public demand for the physical theatre wains, prices will drop, actors salaries will go down, and people will return to the movies again.
--Dave
What would be interesting is if an automated tool were developed specifically to convert sites to a 508 compliant standard (for those not in the Government, Section 508 details all the rules for creating an electronically accessable web site).
One major fault of developers is feeling that it is necessary to create one site that is usable by blindreaders such as Jaws and conventional browsers. For blindreaders to function properly, the site had to be downgraded to a circa 1996 architecture. This makes the site unpleasent and potentially less usable for the vast majority of non-disabled users. Ideally, a tool should be created that automatically looks at your site, and places the content in deadly dull plain text in a separate URL. This duplicate URL tree would be maintained automatically, and users could access it by clicking on a handicapped icon at the top of the screen.
As for other portions of disability developing (there are many of them), it is just good development practice to not rely on color to denote action (colorblind people have a horible time with redlight greenlight stuff). Small changes like that are just concious actions that the developer can make to make their user community more functional.
--Dave