Design process for accessibility features?

Hello all,
I'm wondering if anyone might know where I can find some insight into how the iPad - specifically the accessibility features - was designed. I've found some speculation and one interview with a designer, but does Apple itself make its design process public? Or is it all proprietary?
I hope this is the right forum - I scoured the website for a more appropriate one, but couldn't find it.

Basically it's all proprietary. Apple tends to be very secretive about their design process. The available features are easily found:
http://www.apple.com/ipad/features/accessibility.html
and some general information:
http://www.apple.com/accessibility/
but how Apple decided what specifically to address in a given product and how they approached it generally won't get discussed in public. If you are a media representative working on a story, you might try Apple's PR department and see if they can provide insight or connect you with someone who can:
http://www.apple.com/pr/
but if you're enquiring as a private citizen, there's not much you're likely to be able to discover.
As to the forum, there really isn't a particular forum for these sorts of questions, since the Discussions are for technical support issues. This forum is as good as any, and the Hosts probably will allow the thread to remain as long as it doesn't become a poll or a complaint thread.
Regards.

Similar Messages

  • SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

    I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
    On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In  Installation Progress after some progress installation fails.
    Windows show the following components couldn't installed:
    Managment Tools Complete  Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
    Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
    In detail for failure of every component it provide these details:
    Action required:
    Use the following information to resolve the error, and then try the setup process again.
    Feature failure reason:
    An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    In summary log file it provide the following details:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068643839
      Start time:                    2012-07-31 16:23:37
      End time:                      2012-07-31 16:33:32
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
      Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
      Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  Haansi-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    Database Engine Services                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SQL Server Replication                   1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SharedTools                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.50.1617.0    No        
      SQL Server 2012                                                         
    LocalDB                                  1033                
    Express Edition      11.0.2318.0     No        
      SQL Server 2012                                                         
    Reporting Services - SharePoint                                                   
    11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Developer
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  TABULAR
      ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Manual
      ASSYSADMINACCOUNTS:            PC\Haansi
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SS2012
      INSTANCENAME:                  SS2012
      ISSVCACCOUNT:                  NT Service\MsDtsServer110
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Manual
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Data Tools
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Client Connectivity SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

    Please help. 
    I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068037632
      Start time:                    2014-09-29 15:05:38
      End time:                      2014-09-29 15:15:55
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SSDTBI_VS2012:   Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  MSBI
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2008                                                          Management Tools - Basic  
                  1033                 Express Edition      10.0.1600.22    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          SQL Server Data Tools    
                   1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:         C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
      Installation edition:          Express
      Slipstream:                    True
      SP Level                       1
      Patch Level:                   11.1.3128.0
    Product Update Status:
      Success: KB 2674319, KB 2793634
    Product Updates Selected for Installation:
      Title:                         Service Pack 1
      Knowledge Based Article:       KB 2674319
      Version:                       11.1.3000.0
      Architecture:                  x86
      Language:                      1033
      Title:                         SQL Server 2012 SP1 GDR Product Update
      Knowledge Based Article:       KB 2793634
      Version:                       11.1.3128.0
      Architecture:                  x86
      Language:                      All
      Update Source:                 MU
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SSDTBI_VS2012, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files (x86)\Microsoft SQL Server\
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
    Detailed results:
      Feature:                       SQL Server Data Tools - Business Intelligence for Visual Studio 2012
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio Tools for Applications 2012
      Component error code:          0x80044000
      Component log file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
      Error description:             VS Shell 2012 installation has failed with exit code -2147205120.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

  • 3.1 update indicates home button can be used for accessibility features

    The release list says "Option to use Home button to turn on accessibility features on iPhone 3GS" whic i assumed were things like bluetooth and wifi.. when i go to setting to set the home button there does not appear to be such an option. Does anyone know if this is what was meant and how to do it?

    Mollypia wrote:
    Does anyone know if this is what was meant and how to do it?
    It's not what you assumed. This explains what accessibility features are and how to use them: http://www.apple.com/iphone/how-to/#accessibility.accessibility-features

  • Suggestion for Accessibility features

    I recently purchased the Master Collection CS4. I knew this before I bought it, but a lot of the short cuts that are built into, say a product like Illustrator or Photoshop, are extremely difficult or impossible to use for the physically disabled.
    I realize that Microsoft does have its "sticky keys", but it's not the fastest or easiest way to do things. For example, turning on sticky keys requires the shift key FIVE TIMES.
    Anyone who wants to try to use the applications ONE-HANDED should.
    How about Adobe add an Accessibility Mode (easily able to toggle on and off) or something and in this mode instruct the application like Illustrator or Photoshop to watch for events in series (like if the user first presses CTRL, then shift, it would be the same as CTRL SHIFT).
    I would think Adobe would jump at the chance to attract new customers to the fold. With all of the disabled from youth, accident victims, disabled vets out there, there is the potential for a lot of them to become Adobe customers.
    A lot of the time, the government would be paying for the software to enable them to (re-)enter the workforce.
    Just something to think about.
    Steve

    You should add that to the Features Requests Forum here;
    http://www.adobeforums.com/webx?13@@.eed519b

  • Do you recommend upgrading from Acrobat X to XI from an Accessibility feature standpoint?

    I believe my workload will start to include me making documents accessible. Is there a significant difference in sophistication of the Accessibility features? I saw that there were 'improvements' from X but could I still do just as well (working efficiently) with X for a while? Thank you in advance.

    It has been awhile since I used X. As I recall XI offered enough small improvements all around that it seemed well worthwhile to me to upgrade. But for accessibility features alone - not sure. The accessibility checker in XI seems better than X, but neither is really adequate in my opinion. The free PDF Accessibility Checkers (PAC version 1.3 and 2) from the Swiss foundation Access for All are far more thorough. I would never rely on either Acrobat checker on its own. In short, X worked fine for me for accessibility work, XI is a bit better, both need PAC backup if you are serious about accessibility.

  • Assertion_Failed dump when accessing Design Time for Processes & Forms EP3

    After exhausting SAP note searches and the SDN community forums, blogs & wiki searches, I decide to make my first SDN post:
    After installing Enhancement Pack 3 to the base ECC 6.0, we got the Design Time for Processes & Forms node in the IMG under HR Administrative Services. I was able to get in to it the very first time without any issues; however once I selected one of the sample SAP processes, I received an "Assertion_Failed" dump in the section of code saying a referenced node must exist. In debugging, we did see a node that is referencing a node that does not exist,  which is causing the dump. The dump occurs in CL_HRASR00_DT_OBJECT_BROWSER, Method ASSERT_OBJ_HIER_IS_CONSISTENT (line 71). 
    I now get this dump each time I try to execute the Design Time for Processes & Forms node in the IMG. Note: when accessing process the old way, there is no issue.
    To me is seems like either EP3 was not installed completely, something went wrong in the activation of those business functions, or the copy of the sample forms from client 000 did not grab everything.  In debugging, it appears that the missing reference node is related to some form scenario node.   Also note that all the steps under Technical Settings were completed.
    Has anyone seen this issue before?
    Thanks for any help you can give.  If I find the solution, I will post the answer here as well.
    -Jeff Glynn
    Edited by: Jeffrey Glynn on Oct 22, 2008 1:54 AM

    Hi Jeff,
    I believe we had the same issue here.
    There is an SAP Note (below) for this. Please let me know if this works.
    Note 1075650 - New Design Time tool Corrections for the dump
    Note Language: English Version: 1 Validity: Valid from 18.07.2007
    Summary
    Symptom
    Dump on executing the transaction HRASR_DT which starts the new design time
    tool of the HR Administrative services
    More Terms
    Design time tool HRASR_DT HRadmin
    Cause and Prerequisites
    Solution
    The solution to the dump occuring would be resolved by applying the SP
    Alternately the dump can be
    resolved by performing the following steps manually :
    1.Start SE16 transaction
    2.Give the table name as T5ASRDTOBJHIER and press RETURN key
    3.Execute the Selection screen by pressing on F8 Key
    4.Select the following entries:
    i. OBJECT TYPE = PROCESS and NODE TYPE = PROC_REF_FSCN_DIRECT
    ii.OBJECT TYPE = PROCESS and NODE TYPE = PROC_REF_FSCN_DIRECT_START
    5. Click on EDIT entries button on the header
    6. Enter in the field REF_OBJECT_TYPE the value as FORM_SCENARIO
    7. Click on the Next button on the header bar to navigate to the next entry
    8. Repeat Step 6 for this entry also
    9. Save the modification
    Additionaly, perform the following steps as well:
    1.Start SE16 transaction
    2.Give the table name as T5ASRDTTOOLS and press RETURN key
    3.Execute the Selection screen by pressing on F8 Key
    4.Click on CREATE entry button on the header
    5.Enter the following to create a new entry:
    TOOL TYPE = FSCN_MSG_MAPPER
    OPERATION = DISPEDIT
    TOOL CLASSNAME = CL_HRASR00_DT_FST_MESSAGE_MAP
    6. Enter the following to create a new entry:
    TOOL TYPE = PROC_EXEC_FREQUENCY
    OPERATION = DISPEDIT
    TOOL CLASSNAME = CL_HRASR00_DT_PRT_EXEC_FREQ
    7. Save the new entries
    These adjustments should resolve the dumps hindering to start the new
    design time tool

  • Design Time for Processes and Forms

    Hi experts,
    When trying to open  "Design Time for Processes and Forms" in order to create a process, I get a dump.
    Could you let me know what could be wrong ? config? etc..
    Hereunder is a sample of what I found in T.code ST22
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
        referenced node must exist
          READ TABLE object_hierarchy_nodes TRANSPORTING NO FIELDS
                     WITH KEY node_id = object_hierarchy_node_wa-ref_node_id
    >>>      ASSERT sy-subrc = 0.
        ENDIF.
      provider has to be specified (except in case of recursion)
        IF object_hierarchy_node_wa-ref_node_id IS INITIAL.
          ASSERT object_hierarchy_node_wa-provider_id IS NOT INITIAL.
        ENDIF.
    Thanks in advance,
    Louis

    note: Note 1075650
    Re: Assertion_Failed dump when accessing Design Time for Processes & Forms EP3
    regards,
    Prakesh.

  • Design Time for processes and forms : Short Dump

    Hi All,
    When I try to execute Design Time for processes and forms - (tcode :HRASR_DT), I am getting below short dump.
    The following syntax error occurred in program
    "CL_HRASR00_DT_FSCN_PD_DATA====CP " in include
    "CL_HRASR00_DT_FSCN_PD_DATA====CM00E " in
    line 177:
    "The obligatory parameter "FORM_SCENARIO_VERSION" had no value assigned"
    " to it."
    Please suggest what could resolve this.
    Thanks.
    Tejas

    note: Note 1075650
    Re: Assertion_Failed dump when accessing Design Time for Processes & Forms EP3
    regards,
    Prakesh.

  • Feature of JSP for access command of UNIX

    hello sir ,
    I interesting JSP for developer application on internet . Now , I would like feature of JSP that
    what JSP use command for access comand of UNIX example ls ,mail ,bg (background process) and
    return result of command example mail, bg (background process) to JSP ? please tell me too . Thank you very much.

    thank you for reply question to me
    Please talk detail about runtime & process class to me please and example for JSP call command UNIX "mail" via JSP :-)

  • Design Pattern for simple AIA processes

    I have been using AIA Foundation Pack v2.4 with SOA Suite 10.1.3.4 for a while now and have developed a variety of interfaces using the standard AIA model of:
    Source Adapter (ESB)
    Requester ABCS (BPEL)
    Enterprise Business Service (ESB)
    Provider ABCS (BPEL)
    Target Adapter (ESB)
    I can see the value in usng this model but we are coming up with requirements for more specific Application to Application Integrations where we may just be interfacing some reference data. Therefore there is no available EBO and it is also overkill to develop 5 separate processes to satisfy a simple integration that could be developed with a simple ESB process.
    Are there any best practices or preffered design models for implementing this kind of simple interface but still make use of some of the functionality of the AIA Foundation Pack, such as CAVS, Error Handling and setting dynamic endpoints etc..
    We are also looking to utilise the Service Registry so we can define and manage the differnet services that we have developed.
    I'd be interested to hear peoples thoughts.
    Regards
    Stuart

    In the process of attacking daFei (a truly pointless excercise) everybody forgot to answer the OPs question.
    Here's my take: composition will work better for this. There are several approaches you could use. One is to make a basic concrete Command and put the minimal base properties in it and let the other Command classes wrap other commands without copying.
    Another approach would be to make this class a holder for all the possible attributes. The advantage is that in the above situatiuon (and your current situation, I beleive) one command can be created from another where they share properties that are not in the root set of attributes but these specialized properties will be lost in the copy. You can deal with this through a number of hacks but none are especially pretty. The downside is that you create a kind cyclic dependency by doing this.
    Lastly and people will probably balk at this: you can put the properties in a map and encapsulate this inside each of your command classes. Then copying one from the other is just a matter of cloning the map or just wrapping the same instance, depending on what you want. This addresses theissue described in the paragraph above without creating cyclic dependencies. The downside is that you lose some type checking but you can mitigate to a large degree this by using static literals to get an put values and only access the map through methods specific to each property.

  • Create Adobe Form using Design Time for Processes and Forms

    Hi all,
    I am trying to create a form that have 3 fields:
    1. pernr
    2. ename
    3. effective_date
    I done all the necessary setup of BADI ,class, interface and form.
    I need the step to step guide where you create the adobe form using the Design Time for Processes and Forms. Anyone have any idea?
    Edited by: Siong Chao on Jan 3, 2011 4:54 AM
    Edited by: Siong Chao on Jan 3, 2011 5:00 AM

    Hi,
    I couldn't get to your query..
    What do you mean by step by step procedure for a design time & process for forms.
    if you are a beginner and looking for basic examples to implement adobe forms there are lot of them in SDN, please search them.
    let me know if your query was a very specific one.
    Cheers,
    Sai

  • Best practice in Infoprovider & Query design for access by BO Universe

    Hello Experts,
    Are there any best practices identified by practitioners or suggested by SAP for development of Infoprovider and queries for access by BO Universe.
    Best practices should be from the prospective of performance, design simplicity, adaptability to change etc.
    Appreciate your help.
    Regards,
    Pritesh.
    Edited by: pritesh prakash on Jul 19, 2010 10:51 AM

    Thanks Suresh.
    My project plan is to build Infocubes & queries which will be then used to build Universe upon it. Thus I am looking for do's & dont's while designing infocubes & queries such that there wont be any issues(performance or other) when accessed by Universe built on it.
    Hope I have made it more clear now.
    Regards,
    Pritesh.

  • Best practices or design framework for designing processes in OSB(11g)

    Hi all,
    We have been working in oracle 10g, now in the new project we are going to use Soa suite 11g.For 10g we designed our services very similar to AIA framework. But in 11g since OSB is introduced we are not able to exactly fit the AIA framework here because OSB has a structure different than ESB.
    Can anybody suggest best practices or some design framework for designing processes in OSB or 11g SOA Suite ?

    http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/04_osb.htm
    http://www.oracle.com/technology/products/integration/service-bus/index.html
    Regards,
    Anuj

  • Do we have any third party FLEX component libraries to support accessibility feature for all the components(like: ViewStack, ToggleButtonBar, charts and etc..) ?

    I am working on FLEX 4.6 SDK it provides 35 components with built in accessibility support. My Application contains some components which have no built in accessibility support but I need to provide accessibility support for those components too. I have gone through the Flex docs to customize the non accessible components to support accessibility feature, But the docs where not clear. To customize a single component I have to overwrite lot of code in SDK level.
    and it takes lot of effort.
    So, I would like to use FLEX component libraries which provides accessibility support for all the component.
    Could you please guide me how can I provide accessibility support for other components with out putting more effort on it.
    Thanks in advance...

    There is already such thing in myfaces called "security context" [1]. You could find build of sandbox.jar [2]
    [1] http://myfaces.apache.org/sandbox/securityContext.html
    [2] http://people.apache.org/builds/myfaces/nightly/

  • Entering custom backend service in Design Time for Processes and Forms

    Hi all,
    I am trying to create a form that have 3 fields:
    1. pernr
    2. ename
    3. effective_date
    I done all the necessary setup of BADI ,class, interface and form.
    However I cannot seem to insert my custom backend service in the Design Time for Processes and Forms workbench (t-code:hrasr_dt).
    Currently, I am just using SAP_PA for my backend service which is unable to load the ename into my form. The code in my custom class will not be triggered if I did not use my custom back end service in the Design Time for Processes and Forms.
    Whenever I tried using my custom back end service, I will encounter the assertion_failed dump.
    Anyone have any idea?
    Edited by: Siong Chao on Dec 22, 2010 6:35 AM

    Hi Siong Chao,
    The filter name you have used in the BADI for your generic service requires to be defined in the Create / Edit Generic Service - Definition.( You can see this on selecting the Back-end services node under Form Scenario definition while using HRASR_DT transaction code)
    Once you do that, you can import the fields defined in the Generic service BADI - using the same procedure used in standard SAP backend sevices.
    Hope this clarifies. Please let me know if you have any further questions.
    Best Regards
    G Raj

Maybe you are looking for